-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Package sonar-channel that is removed from SonarQube plugin API 7.4 #227
Conversation
By default sonar-channel is not packaged into sonarqube plugin, because sonarqube plugin API v6.7 provides them to plugin. However, SonarQube 7.4 does not provide them to plugins, so we plugin provider need to package them by own. https://jira.sonarsource.com/browse/SONAR-10331?focusedCommentId=190952&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-190952
I'm investigating why |
25de4c9
to
bbf05ff
Compare
@h3xstream @VinodAnandan Our build in this branch is now stable, please review and merge this. |
@h3xstream @VinodAnandan , Can someone please merge this changes. We are in process of Migration of SonarQube from 6.7 to 7.4. |
LGTM |
Smoke Test failed. |
I've checked its build log and it seems that Travis' filesystem had some trouble to create directory.
I'll rerun failed builds, to ensure that |
3.9.1 is now published at Maven central. |
When will this be available in SonarQube Marketplace? |
@ddcruver I strongly recommend you to install from Maven central. Release to Marketplace always takes long time. At least, we need to wait three days to get feedback like this, then again wait several days (or weeks) to deploy artifact to marketplace like this. |
@VinodAnandan 3.9.0 has been released to marketplace, so I made a topic regarding RFF for 3.9.1. |
Thank you @KengoTODA |
I also posted the request to deploy 3.9.1 at sonarsource forum. |
Finally 3.9.1 has been published to marketplace. |
As described in #225,
sonar-channel
andcommons-io
has been removed from SonarQube plugin API 7.4. This is why the build with SonarQube plugin API 7.4 is failing, and sonar-findbugs 3.9 lacks compatibility with SonarQube 7.4.In this PR, I reproduce reported issue #226 by smoke test, and fix it by packaging
sonar-channel
andcommons-io
into sonar-findbugs. We need to usemaven-shade-plugin
becausesonar-packaging-maven-plugin
does not package these two libraries. Here is message:So to support both SonarQube 6.7 and 7.4, we need to shade these libraries. To avoid classloader related issue, I also changed their package path.
This PR closes #225 and #226.